

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>Version Control &amp; Team Deployment [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Version Control,Version Control In Team Deployment,Version Control Configuration, Team Deployment,Version Control Branching,Team Deployment,Team Deployment And Version Control,Team Deployment Version Control Branching">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <p class="p_Heading1"><span class="f_Heading1">Version Control &amp; Team Deployment</span></p>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="applying_version_control_to_en.htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="vcmenu2.htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_BodyText"><span class="f_BodyText">Team deployment and the use of version control is discussed in two Sparx Systems white papers, available on the Sparx Systems web site:</span></p>
<ul style="text-indent: 0px; margin-left: 30px; list-style-position: outside;">
<li><span class="f_Bulletlist1"><a href="http://sparxsystems.com/WhitePapers/Version_Control.pdf" target="_blank" class="weblink">http://sparxsystems.com/WhitePapers/Version_Control.pdf</a></span></li>
<li><span class="f_Bulletlist1"><a href="http://sparxsystems.com/downloads/whitepapers/EA_Deployment.pdf" target="_blank" class="weblink">http://sparxsystems.com/downloads/whitepapers/EA_Deployment.pdf</a></span></li>
</ul>
<p class="p_BodyText"><span class="f_BodyText">A brief summary of the process is provided below:</span></p>
<ol style="text-indent: 0px; margin-left: 48px; list-style-position: outside;">
<li value=1><span class="f_NumberedList">Install your version control product.</span></li>
<li value=2><span class="f_NumberedList">Create a version control repository.</span></li>
<li value=3><span class="f_NumberedList">Create a version control project to be used with your Enterprise Architect project, and check-out a working copy of the project into a local folder. (You must do this for every team member that is accessing the version controlled packages, whether you are using a single shared model or each team member stores his own private copy of the model.)</span></li>
<li value=4><span class="f_NumberedList">Within Enterprise Architect, <a href="versioncontrolsetup.htm">define a version control configuration</a> to provide access to the working copy files. Again, each user must do this on their own workstation, as the details are stored within the Windows registry.</span></li>
<li value=5><span class="f_NumberedList"><a href="configure_package_for_version_.htm">Configure packages</a> within the Enterprise Architect model for version control. That is, apply version control to individual packages.</span></li>
<li value=6><span class="f_NumberedList"><a href="checkinginandcheckingoutp.htm">Check-out and check-in packages</a> as required.</span></li>
</ol>
<div style="text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 5px 0px 5px 13px;"><table cellspacing="0" cellpadding="2" border="0" style="border: none; border-spacing:0px;">
<tr style="text-align:left;vertical-align:bottom;">
<td valign="bottom" width="955" bgcolor="#efeff7" style="width:955px; background-color:#efeff7;"><p class="p_TiporNote" style="border-top: none; border-right: none; border-left: none;"><span class="f_TiporNote">Note:</span></p>
</td>
</tr>
<tr style="text-align:left;">
<td width="955" bgcolor="#f7f7ff" style="width:955px; background-color:#f7f7ff;"><p class="p_TiporNoteText"><span class="f_TiporNoteText">The name of the version control configuration must be the same across all machines. That is, all version control access to a given Enterprise Architect package must be through version control configurations with the same name, across all models and all users. (It is possible to use multiple version control configurations within the same model, so different packages can still use different version control configurations within the same model, as long as any given package is always accessed via the same version control configuration.)</span></p>
</td>
</tr>
</table>
</div>
<p class="p_BodyText"><span class="f_BodyText">The easiest way to perform step 4, (throughout the team), is to have one user set up version control on the model and then share that model with the rest of the team.</span></p>
<ul style="text-indent: 0px; margin-left: 30px; list-style-position: outside;">
<li><span class="f_Bulletlist1">In Shared Model deployment, all users connect to a single instance of the model database, so the model is shared automatically.</span></li>
<li><span class="f_Bulletlist1">In Private Model deployment, it is easiest to distribute copies of the original model (after version control has been set up) to all other members of the team.</span></li>
</ul>
<p class="p_BodyText"><span class="f_BodyText">Whenever you open a model (<a href="versioncontrol.htm#Usage">Private or Shared</a>) that uses a version control configuration that is not yet defined on your workstation, Enterprise Architect prompts you to complete the definition for that configuration. This typically means specifying the local working copy directory and maybe choosing the version control project associated with this Enterprise Architect project.</span></p>
<p class="p_BodyText"><span class="f_BodyText">Once this has been done, the version controlled packages that already exist in the model are ready for use.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Version Control Branching</span></p>
<p class="p_BodyText"><span class="f_BodyText">Currently, Enterprise Architect does not support Version Control Branching. Work-arounds to achieve similar results might be possible for certain version-control products; contact Sparx Support for advice:</span></p>
<ul style="text-indent: 0px; margin-left: 30px; list-style-position: outside;">
<li><span class="f_Bulletlist1">Registered users -<a href="http://www.sparxsystems.com/registered/reg_support.html" target="_blank" class="weblink"> http://www.sparxsystems.com/registered/reg_support.html</a></span></li>
<li><span class="f_Bulletlist1">Trial users - <a href="mailto:support@sparxsystems.com" target="_blank" class="weblink">support@sparxsystems.com</a>.</span></li>
</ul>




            </div>
          </div>
        </div>



</div>


</body>
</html>
